Censys Related Infrastructure

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Content Index

This playbook retrieves related infrastructure details for Censys entities (hosts, certificates, or web properties) using the Censys Pivot Analysis API. It accepts an IOC Value (hosts, certificates, or web properties) and IOC type as input, creates a pivot analysis job, monitors the job status, retrieves the results, and ingests the related infrastructure data into Azure Log Analytics for further analysis and display data in the dashboard. Learn more about CensEye in the Censys documentation: ht

Attribute	Value
Type	Playbook
Solution	Censys
Source	View on GitHub

Tables Used

This content item queries data from the following tables:

Table	Transformations	Ingestion API	Lake-Only
`CensysRelatedInfrastructure_CL` 🔶	?	✓	?

Logic App Connectors

This playbook uses 3 Logic App connectors / built-in actions:

Connector / Action	Type	Connections	Actions
`azureloganalyticsdatacollector`	Managed	1	1
`keyvault`	Managed	1	1
`http`	Built-in	0	3

Action parameters (URLs, paths, function IDs)

`azureloganalyticsdatacollector` (Managed)

Action	Method	Endpoint	Other
Send_Related_Infrastructure_to_Log_Analytics_Workspace	post	`/api/logs`	—

`keyvault` (Managed)

Action	Method	Endpoint	Other
Get_Censys_API_Key	get	`/secrets/@{encodeURIComponent('Censys-Access-Token')}/value`	—

`http` (Built-in)

Action	Method	Endpoint	Other
HTTP_Post_Request_To_Create_Pivot_Analysis_Job	POST	`@{variables('base_url')}/@{variables('api_version')}/@{variables('pivot_analysis_job_endpoint')}`	—
HTTP_Call_to_Fetch_Job_Status	GET	`@{variables('base_url')}/@{variables('api_version')}/@{variables('pivot_analysis_job_endpoint')}/@{variables('job_id')}`	—
HTTP_Call_to_Fetch_Job_result_data	GET	`@{variables('base_url')}/@{variables('api_version')}/@{variables('pivot_analysis_job_endpoint')}/@{variables('job_id')}/results`	—

Additional Documentation

📄 Source: CensysRelatedInfrastructure/readme.md

Summary

Prerequisites

Obtain a Censys API token and store it in Azure Key Vault as a secret named 'Censys-Access-Token'.
Obtain the Censys Organization ID from your Censys platform account.
Create or identify an Azure Key Vault and note its name and Tenant ID.
Ensure you have a Log Analytics Workspace configured for Microsoft Sentinel.
Deploy the Censys Related Infrastructure workbook to use this playbook.

Deployment Instructions

To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
Fill in the required parameters:
- PlaybookName: Enter the playbook name here (default: CensysRelatedInfrastructure).
- OrganizationID: Your Censys Organization ID from the Censys platform account settings.
- KeyVaultName: Name of the Azure Key Vault where the Censys API token is stored.
- TenantId: Azure AD Tenant ID where the Key Vault is located.

Post-Deployment Instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

Go to your logic app → API connections → Select Key Vault connection resource.
Go to General → edit API connection.
Click Authorize.
Sign in.
Click Save.
Repeat steps for Log Analytics Data Collector connection.

b. Add Access policy in Keyvault

Add access policy for the playbook's managed identity to read secrets from Key Vault.

Go to logic app → your logic app → identity → System assigned Managed identity and copy Object (principal) ID.
Go to keyvaults → your keyvault → Access policies → create.
Select Get and List permissions for Secrets. Click next.
In the principal section, search by copied object ID. Click next.
Click review + create.